Edit - The Workplace Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

1

This is what I was thinking. And I would extend this answer a bit: ask the candidate to describe how they've approached large code bases in the past. What they've done. Try to drill down a bit. Try to get them talking and see if they can respond fluidly or if they can only talk in generalities.

DaveG
– DaveG

2024-12-04 16:53:05 +00:00
Commented Dec 4, 2024 at 16:53

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »